This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@tanstack/ai@0.43.0

Minor Changes

• #955 7c7aa09 - Resumable streams: reconnect to an in-flight SSE or NDJSON response without
  re-running the provider.

  toServerSentEventsResponse and toHttpResponse both accept a
  durability: { adapter, batch } option. The adapter (StreamDurability)
  records every chunk to an ordered log before delivery and tags each event with
  an opaque, adapter-owned offset — an SSE id: line, or the id of an NDJSON
  { id, chunk } envelope (NDJSON has no native event-id). A reconnect
  (Last-Event-ID) or an explicit ?offset read replays strictly after that
  offset from the log — the lazy provider stream is never iterated on resume.
  Producers terminalize the log on cancellation and failure (RUN_ERROR append

  • close()) and on completion when the source stream emits its own terminal
    event (chat() always does), so readers are never parked on a dead run.

  Two adapters ship: memoryStream(request) in @tanstack/ai (process-local,
  for development and tests) and the new @tanstack/ai-durable-stream package,
  a Durable Streams protocol adapter for production backends.

  For the GET handler that a reload or a second tab reconnects to,
  resumeServerSentEventsResponse({ adapter }) and resumeHttpResponse({ adapter })
  replay a run straight from the durability log. They need no producer stream and
  return a 400 when the request carries no resume offset.

  On the client, all four HTTP adapters are now resumable — fetchServerSentEvents,
  fetchHttpStream, xhrServerSentEvents, and xhrHttpStream. Each tracks the
  per-event offset, auto-reconnects with Last-Event-ID, de-duplicates the
  replayed prefix, and exposes joinRun(runId) to attach to an in-flight or
  finished run from the start (read-only GET with offset=-1). Untagged streams
  behave exactly as before. A durable run that ends with no terminal event and no
  forward progress now throws DurableStreamIncompleteError instead of hanging.

  Reconnection and durability are bounded so failures surface rather than hang or
  loop:

  • memoryStream evicts completed logs after a grace window (unbounded growth
    is gone); resuming an expired/unknown run throws, and a from-start join to a
    run that never produces fails after MemoryStreamOptions.firstChunkDeadlineMs.
  • all four HTTP adapters accept reconnect: { maxAttempts, delayMs } — a
    throttle plus a ceiling on CONSECUTIVE no-progress reconnects (default 5;
    forward progress resets it) that fails with the new StreamReconnectLimitError
    instead of reconnecting endlessly, without penalizing a healthy long-lived run.
  • durableStream accepts reconnect: { maxReadFailures, delayMs } to bound its
    read-retry loop, and server is now optional when fetch is provided (e.g. a
    Cloudflare service binding).
  • toServerSentEventsResponse accepts debug to record durability terminal /
    close failures server-side, where a replaying joiner cannot observe them.

@tanstack/ai-client@0.23.0

Minor Changes

• #955 7c7aa09 - Resumable streams: reconnect to an in-flight SSE or NDJSON response without
  re-running the provider.

  toServerSentEventsResponse and toHttpResponse both accept a
  durability: { adapter, batch } option. The adapter (StreamDurability)
  records every chunk to an ordered log before delivery and tags each event with
  an opaque, adapter-owned offset — an SSE id: line, or the id of an NDJSON
  { id, chunk } envelope (NDJSON has no native event-id). A reconnect
  (Last-Event-ID) or an explicit ?offset read replays strictly after that
  offset from the log — the lazy provider stream is never iterated on resume.
  Producers terminalize the log on cancellation and failure (RUN_ERROR append

  • close()) and on completion when the source stream emits its own terminal
    event (chat() always does), so readers are never parked on a dead run.

  Two adapters ship: memoryStream(request) in @tanstack/ai (process-local,
  for development and tests) and the new @tanstack/ai-durable-stream package,
  a Durable Streams protocol adapter for production backends.

  For the GET handler that a reload or a second tab reconnects to,
  resumeServerSentEventsResponse({ adapter }) and resumeHttpResponse({ adapter })
  replay a run straight from the durability log. They need no producer stream and
  return a 400 when the request carries no resume offset.

  On the client, all four HTTP adapters are now resumable — fetchServerSentEvents,
  fetchHttpStream, xhrServerSentEvents, and xhrHttpStream. Each tracks the
  per-event offset, auto-reconnects with Last-Event-ID, de-duplicates the
  replayed prefix, and exposes joinRun(runId) to attach to an in-flight or
  finished run from the start (read-only GET with offset=-1). Untagged streams
  behave exactly as before. A durable run that ends with no terminal event and no
  forward progress now throws DurableStreamIncompleteError instead of hanging.

  Reconnection and durability are bounded so failures surface rather than hang or
  loop:

  • memoryStream evicts completed logs after a grace window (unbounded growth
    is gone); resuming an expired/unknown run throws, and a from-start join to a
    run that never produces fails after MemoryStreamOptions.firstChunkDeadlineMs.
  • all four HTTP adapters accept reconnect: { maxAttempts, delayMs } — a
    throttle plus a ceiling on CONSECUTIVE no-progress reconnects (default 5;
    forward progress resets it) that fails with the new StreamReconnectLimitError
    instead of reconnecting endlessly, without penalizing a healthy long-lived run.
  • durableStream accepts reconnect: { maxReadFailures, delayMs } to bound its
    read-retry loop, and server is now optional when fetch is provided (e.g. a
    Cloudflare service binding).
  • toServerSentEventsResponse accepts debug to record durability terminal /
    close failures server-side, where a replaying joiner cannot observe them.

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-durable-stream@0.1.0

Minor Changes

• #955 7c7aa09 - Resumable streams: reconnect to an in-flight SSE or NDJSON response without
  re-running the provider.

  toServerSentEventsResponse and toHttpResponse both accept a
  durability: { adapter, batch } option. The adapter (StreamDurability)
  records every chunk to an ordered log before delivery and tags each event with
  an opaque, adapter-owned offset — an SSE id: line, or the id of an NDJSON
  { id, chunk } envelope (NDJSON has no native event-id). A reconnect
  (Last-Event-ID) or an explicit ?offset read replays strictly after that
  offset from the log — the lazy provider stream is never iterated on resume.
  Producers terminalize the log on cancellation and failure (RUN_ERROR append

  • close()) and on completion when the source stream emits its own terminal
    event (chat() always does), so readers are never parked on a dead run.

  Two adapters ship: memoryStream(request) in @tanstack/ai (process-local,
  for development and tests) and the new @tanstack/ai-durable-stream package,
  a Durable Streams protocol adapter for production backends.

  For the GET handler that a reload or a second tab reconnects to,
  resumeServerSentEventsResponse({ adapter }) and resumeHttpResponse({ adapter })
  replay a run straight from the durability log. They need no producer stream and
  return a 400 when the request carries no resume offset.

  On the client, all four HTTP adapters are now resumable — fetchServerSentEvents,
  fetchHttpStream, xhrServerSentEvents, and xhrHttpStream. Each tracks the
  per-event offset, auto-reconnects with Last-Event-ID, de-duplicates the
  replayed prefix, and exposes joinRun(runId) to attach to an in-flight or
  finished run from the start (read-only GET with offset=-1). Untagged streams
  behave exactly as before. A durable run that ends with no terminal event and no
  forward progress now throws DurableStreamIncompleteError instead of hanging.

  Reconnection and durability are bounded so failures surface rather than hang or
  loop:

  • memoryStream evicts completed logs after a grace window (unbounded growth
    is gone); resuming an expired/unknown run throws, and a from-start join to a
    run that never produces fails after MemoryStreamOptions.firstChunkDeadlineMs.
  • all four HTTP adapters accept reconnect: { maxAttempts, delayMs } — a
    throttle plus a ceiling on CONSECUTIVE no-progress reconnects (default 5;
    forward progress resets it) that fails with the new StreamReconnectLimitError
    instead of reconnecting endlessly, without penalizing a healthy long-lived run.
  • durableStream accepts reconnect: { maxReadFailures, delayMs } to bound its
    read-retry loop, and server is now optional when fetch is provided (e.g. a
    Cloudflare service binding).
  • toServerSentEventsResponse accepts debug to record durability terminal /
    close failures server-side, where a replaying joiner cannot observe them.

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-acp@0.2.4

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-sandbox@0.2.5

@tanstack/ai-angular@0.3.2

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-client@0.23.0

@tanstack/ai-anthropic@0.16.4

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-bedrock@0.1.5

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/openai-base@0.9.10

@tanstack/ai-claude-code@0.2.4

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-sandbox@0.2.5

@tanstack/ai-code-mode@0.3.9

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-code-mode-skills@0.3.12

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-code-mode@0.3.9

@tanstack/ai-codex@0.2.4

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-sandbox@0.2.5

@tanstack/ai-devtools-core@0.4.25

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-elevenlabs@0.2.35

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-fal@0.9.13

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-gemini@0.20.2

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-grok@0.14.10

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/openai-base@0.9.10

@tanstack/ai-grok-build@0.2.4

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-acp@0.2.4
  • @tanstack/ai-sandbox@0.2.5

@tanstack/ai-groq@0.5.4

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/openai-base@0.9.10

@tanstack/ai-isolate-cloudflare@0.2.39

Patch Changes

• Updated dependencies []:
  • @tanstack/ai-code-mode@0.3.9

@tanstack/ai-isolate-node@0.1.48

Patch Changes

• Updated dependencies []:
  • @tanstack/ai-code-mode@0.3.9

@tanstack/ai-isolate-quickjs@0.1.48

Patch Changes

• Updated dependencies []:
  • @tanstack/ai-code-mode@0.3.9

@tanstack/ai-mcp@0.2.6

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-mistral@0.2.4

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-ollama@0.8.17

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-openai@0.17.2

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/openai-base@0.9.10

@tanstack/ai-opencode@0.2.4

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-sandbox@0.2.5

@tanstack/ai-openrouter@0.15.11

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-preact@0.11.2

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-client@0.23.0

@tanstack/ai-react@0.18.2

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-client@0.23.0

@tanstack/ai-react-ui@0.8.16

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai-client@0.23.0
  • @tanstack/ai-react@0.18.2

@tanstack/ai-sandbox@0.2.5

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/ai-sandbox-cloudflare@0.2.5

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-sandbox@0.2.5
  • @tanstack/ai-sandbox-local-process@0.2.0

@tanstack/ai-solid@0.15.2

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-client@0.23.0

@tanstack/ai-solid-ui@0.7.15

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai-client@0.23.0
  • @tanstack/ai-solid@0.15.2

@tanstack/ai-svelte@0.15.2

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-client@0.23.0

@tanstack/ai-vue@0.15.2

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0
  • @tanstack/ai-client@0.23.0

@tanstack/ai-vue-ui@0.2.35

Patch Changes

• Updated dependencies []:
  • @tanstack/ai-vue@0.15.2

@tanstack/openai-base@0.9.10

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai@0.43.0

@tanstack/preact-ai-devtools@0.1.68

Patch Changes

• Updated dependencies []:
  • @tanstack/ai-devtools-core@0.4.25

@tanstack/react-ai-devtools@0.2.68

Patch Changes

• Updated dependencies []:
  • @tanstack/ai-devtools-core@0.4.25

@tanstack/solid-ai-devtools@0.2.68

Patch Changes

• Updated dependencies []:
  • @tanstack/ai-devtools-core@0.4.25

ag-ui@0.0.3

Patch Changes

• Updated dependencies [7c7aa09]:
  • @tanstack/ai-client@0.23.0
  • @tanstack/ai-react@0.18.2
  • @tanstack/ai-react-ui@0.8.16